I am working in a Howto for installing ReactOS, so i
tried the diferent ways for instalating it, but in
recent builds there was no option to install the
Freeloader in a diskete (XP machine here) in the Real
Hardware instalation.
I tried downloading the binaries and copying them to
C:\ReactOS , download the Freeloader image and
RAWwrite it in a diskete, but i could not get the
configuration screen (it worked for me, but maybe not
for others without configuration options)
Is there any way i could install the Freeloader image
and still have a "normal" configuration phase of
ReactOS.? This will help convince people to install
reactOS, not having to touch the Boot sector for a
ReactOS insatllation regardless the OS you have
installed would be great. I imagine something like
this:
--------------------------------------
1) Download the ReactOS binaries (8 Megs) from
sourceforge
2) Use Winzip to extract them to C:\ that way a Folder
called C:\ReactOS will be created with all the reactos
files(It must be a FAT32 partition).
3) Download the Program Rawwrite for windows and
extract it to any folder you wish.
4) Download the Freeloader Floopy Disk image and
extract it to any folder you wish.
5) Insert a new formated Floopy Disk and Execute
Rawwrite:
6) Select the image file from the folder you extracted
the Freeloader:
7) Press write, and wait till the program ends writing
the image to the Floopy.
8) Restart the computer booting from the Floopy Disk:
----------------------------------------
This is the option i would like as user. Copy the
program to a folder, and the use a Diskete to load it.
Usefull both in 95/98/NT/XP and Linux, with minimal
risks for people who fears burning their HD.
But the question, Can this be done?. I have downloaded
the source code but i am lost. Can someone help me
with this?
Thanks in advance,
Lucio Diaz.
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
Hi!
Isn't it possible to call NdisIStartAdaper (in ndis/miniport.c) when the
miniport driver recieves an IRP_MJ_PNP/IRP_MN_START_DEVICE request? Right
now it is called from NdisIAddDevice.
This means the miniport device is started before resource lists are assigned
to the NICs device node. NdisMQueryAdaperResources and
NdisMPciAssignResources cannot be implemented oe won't work because of this.
Regards,
Eric
I intend to move the following important software from rosapps to reactos/subsys/system:
calc
regedt32
regsvr32
sysutils/ctm
and the following to reactos/apps/utils/net:
net/ping
net/arp
net/finger
net/ipconfig
net/netstat
net/telnet
net/whois
Actually there are two telnet applications. Which is better?
If I've left out something important, please speak up.
Casper
For a many month I am unable to install ReactOS with DBG=1 and KDBG=1
enabled.
On the same hardware, version with DBG=0 and KDBG=0 installs and runs fine.
DBG=1, KDBG=1 enabled ReactOS booted by freeldr asks for COMUTERNAME,
Name, password, time zone etc. etc. and asks for reboot.
Then it bugchecks with :
bt
Frames: vmwinst.exe: vmwinst.c: 75 (DetectVMware)
bugcheck
KeBugCheck at dbg/kdb.c: 1495
Bug detected (code deaddead param 0 0 0 0)
Page fault at high IRQL was 2
KeBugCheckWithTf at ke/catch.c:165
Bug detected (code 1e param 0 0 0 0)
KMODE_EXCEPTION_NOT_HANDLED
Page fault Exception: 14(0)
Processo: 0 CS:EIP 8:c00b8cb7 <ntoskrnl.exe: rtl/message.c:108
(RtlFindMessage)>
cr2 e07a4604 cr3 1d84a000
Proc: c0eb1c90 Pid:7 <vmwinst> Thrd: c0ebd08 Tid: 2c
DS 10 ES 10 FS 30 GS 10
kernel stack base df255000
KeBugCheckWithTf
KeBugCheckEx
KeBugCheck
DbgBugCheckCommand
KdbDoCommand
KdbMainLoop
KdbInternalEnter
KdbEnterDebuggerException
KiDispatchException
ke/i386/usertrap.c: 139 KiUserTrapHandler
ke/i386/exp.c: 613 KiTrapHandler
/tmp/ccphDdwg.s: 146 KeUserModeCallback
vmwinst.c: 75 DetectVMware
vmwinst.c:1016 WinMain
1047 WinMain
kernel32.dll: BaseProcessStart <DEADBEEF>
If someone is interested in more debugging informations, I can send
processor registers and map files.
Regards,
David
--
David Kredba <kredba at ibot.cas.cz>
GPG: ID 1024D/5B6B02DE
Fingerprint: F0B3312596BEDCF91DFB 0699E06AACD75B6B02DE
PLease find the status of the Reactos support for the Nic Realtek8139 as
per my testing.
1) Detection of Pci Bus2 = Fixed
The problem of enumerating cards located on PCI BUS 2 has been fixed by
Eric Khol . The bug# 436 can be closed
2) Start Nic driver failure
The RTL8139.SYS driver loads successfully but fails to start due to the
"NdisMQueyAdapterResources" function which is unimplemnted .
The Bug#446 has been created
=> This is a blocking point for networking with this popular Nic
Best regards
Gerard
Are you getting this ?
(DBG=1, KDBG=1)
make[1]: Entering directory `/home/dave2/ros/reactos/lib/msafd'
mingw32-gcc -I./include -Wall -Werror -fno-builtin -DUNICODE
-D__USE_W32API -I.-I../../include -I../../w32api/include -pipe
-march=i486 -D_M_IX86 -g -c misc/sndrcv.c -o misc/sndrcv.o
misc/sndrcv.c: In function `WSPRecv':
misc/sndrcv.c:66: error: `AFD_IMMEDIATE' undeclared (first use in this
function)
misc/sndrcv.c:66: error: (Each undeclared identifier is reported only once
misc/sndrcv.c:66: error: for each function it appears in.)
misc/sndrcv.c: In function `WSPRecvFrom':
misc/sndrcv.c:214: error: `AFD_IMMEDIATE' undeclared (first use in this
function)
misc/sndrcv.c: In function `WSPSend':
misc/sndrcv.c:365: error: `AFD_IMMEDIATE' undeclared (first use in this
function)
misc/sndrcv.c: In function `WSPSendTo':
misc/sndrcv.c:503: error: `AFD_IMMEDIATE' undeclared (first use in this
function)
David
--
David Kredba <kredba at ibot.cas.cz>
GPG: ID 1024D/5B6B02DE
Fingerprint: F0B3312596BEDCF91DFB 0699E06AACD75B6B02DE
